Download Developing Solutions for Microsoft Azure.AZ-203.PrepAway.2020-12-01.157q.vcex

Azure Functions can run on either a Consumption Plan or a dedicated App Service Plan. If you run in a dedicated mode, you need to turn on the Always On setting for your Function App to run properly. The Function runtime will go idle after a few minutes of inactivity, so only HTTP triggers will actually "wake up" your functions. This is similar to how WebJobs must have Always On enabled. Scenario: Notification latency: Users report that anomaly detection emails can sometimes arrive several minutes after an anomaly is detected. Anomaly detection service: You have an anomaly detection service that analyzes log information for anomalies. It is implemented as an Azure Machine Learning model. The model is deployed as a web service. If an anomaly is detected, an Azure Function that emails administrators is called by using an HTTP WebHook. References:https://github.com/Azure/Azure-Functions/wiki/Enable-Always-On-when-running-on-dedicated-App-Service-Plan Develop Azure Infrastructure as a Service Compute Solutions

Box 1: groupCreate a resource group with the az group create command. An Azure resource group is a logical group in which Azure resources are deployed and managed. The following example creates a resource group named myResourceGroup in the westeurope location. az group create --name myResourceGroup --location westeurope Box 2: CohoWinterLabelMakerUse the resource group named, which is used in the second command. Box 3: aksThe command az aks create, is used to create a new managed Kubernetes cluster. Box 4: monitoringScenario: LabelMaker appAzure Monitor Container Health must be used to monitor the performance of workloads that are deployed to Kubernetes environments and hosted on Azure Kubernetes Service (AKS). You must use Azure Container Registry to publish images that support the AKS deployment. Develop Azure Infrastructure as a Service Compute Solutions

Before you can connect to on-premises data sources from Azure Logic Apps, download and install the on-premises data gateway on a local computer. The gateway works as a bridge that provides quick data transfer and encryption between data sources on premises (not in the cloud) and your logic apps. The gateway supports BizTalk Server 2016. Note: Microsoft have now fully incorporated the Azure BizTalk Services capabilities into Logic Apps and Azure App Service Hybrid Connections. Logic Apps Enterprise Integration pack bring some of the enterprise B2B capabilities like AS2 and X12, EDI standards support Scenario: The Shipping Logic app must meet the following requirements:Support the ocean transport and inland transport workflows by using a Logic App. Support industry standard protocol X12 message format for various messages including vessel content details and arrival notices. Secure resources to the corporate VNet and use dedicated storage resources with a fixed costing model. Maintain on-premises connectivity to support legacy applications and final BizTalk migrations. References:https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-gateway-install

Plan: StandardStandard support auto-scaling Instance Count: 10Max instances for standard is 10. Scenario: The REST API’s that support the solution must meet the following requirements:Allow deployment to a testing location within Azure while not incurring additional costs. Automatically scale to double capacity during peak shipping times while not causing application downtime. Minimize costs when selecting an Azure payment model. References:https://azure.microsoft.com/en-us/pricing/details/app-service/plans/Develop Azure Infrastructure as a Service Compute Solutions

Step 1: az batch pool create# Create a new Linux pool with a virtual machine configuration.  az batch pool create \ --id mypool \ --vm-size Standard_A1 \ --target-dedicated 2 \ --image canonical:ubuntuserver:16.04-LTS \--node-agent-sku-id "batch.node.ubuntu 16.04" Step 2: az batch job create # Create a new job to encapsulate the tasks that are added. az batch job create \ --id myjob \ --pool-id mypool Step 3: az batch task create# Add tasks to the job. Here the task is a basic shell command. az batch task create \ --job-id myjob \ --task-id task1 \ --command-line "/bin/bash -c 'printenv AZ_BATCH_TASK_WORKING_DIR'"  Step 4: for i in {1..$numberOfJobs} doReferences:https://docs.microsoft.com/bs-latn-ba/azure/batch/scripts/batch-cli-sample-run-job

A Batch job is a logical grouping of one or more tasks. A job includes settings common to the tasks, such as priority and the pool to run tasks on. The app uses the BatchClient.JobOperations.CreateJob method to create a job on your pool. The Commit method submits the job to the Batch service. Initially the job has no tasks. {     CloudJob job = batchClient.JobOperations.CreateJob();     job.Id = JobId;     job.PoolInformation = new PoolInformation { PoolId = PoolId };     job.Commit(); } ... References:https://docs.microsoft.com/en-us/azure/batch/quick-run-dotnet

Box 1: ContinuousContinuous runs on all instances that the web app runs on. You can optionally restrict the WebJob to a single instance. Box 2: TriggeredTriggered runs on a single instance that Azure selects for load balancing. Box 3: ContinuousContinuous supports remote debugging. Note: The following table describes the differences between continuous and triggered WebJobs.     References:https://docs.microsoft.com/en-us/azure/app-service/web-sites-create-web-jobs

With the Azure CLI: Step 1: In the Azure CLI, run the command: az batch account create First we create a batch account. Step 2: In Azure CLI, run the command: az batch pool createNow that you have a Batch account, create a sample pool of Linux compute nodes using the az batch pool create command. Step 3: In Azure CLI, run the command: az batch job createNow that you have a pool, create a job to run on it. A Batch job is a logical group for one or more tasks. A job includes settings common to the tasks, such as priority and the pool to run tasks on. Create a Batch job by using the az batch job create command. Step 4: In Azure CLI, run the command: az batch task createNow use the az batch task create command to create some tasks to run in the job. References:https://docs.microsoft.com/en-us/azure/batch/quick-create-cli

Step 1: az group createCreate a resource group with the az group create command. An Azure resource group is a logical group in which Azure resources are deployed and managed. Example: The following example creates a resource group named myAKSCluster in the eastus location.az group create --name myAKSCluster --location eastus Step 2 : az aks createUse the az aks create command to create an AKS cluster.  Step 3: kubectl applyTo deploy your application, use the kubectl apply command. This command parses the manifest file and creates the defined Kubernetes objects. Step 4: az aks get-credentialsConfigure it with the credentials for the new AKS cluster. Example: az aks get-credentials --name aks-cluster --resource-group aks-resource-group References:https://docs.bitnami.com/azure/get-started-aks/

Step 1: Encrypt the on-premises VHD by using BitLocker without a TPM. Upload the VM to Azure StorageStep 2: Run the Azure PowerShell command Set-AzureRMVMOSDiskTo use an existing disk instead of creating a new disk you can use the Set-AzureRMVMOSDisk command. Example:$osDiskName = $vmname+'_osDisk' $osDiskCaching = 'ReadWrite' $osDiskVhdUri = "https://$stoname.blob.core.windows.net/vhds/"+$vmname+"_os.vhd"$vm = Set-AzureRmVMOSDisk -VM $vm -VhdUri $osDiskVhdUri -name $osDiskName -Create Step 3: Run the Azure PowerShell command Set-AzureRmVMDiskEncryptionExtensionUse the Set-AzVMDiskEncryptionExtension cmdlet to enable encryption on a running IaaS virtual machine in Azure. Incorrect: Not TPM: BitLocker can work with or without a TPM. A TPM is a tamper resistant security chip on the system board that will hold the  keys for encryption and check the integrity of the boot sequence and allows the most secure BitLocker implementation. A VM does not have a TPM. References: https://www.itprotoday.com/iaaspaas/use-existing-vhd-azurerm-vm